TG-332: Add Github action for building Linux kernel#61
TG-332: Add Github action for building Linux kernel#61himanshus2025 merged 16 commits intotg-v6.12from
Conversation
himanshus2025
force-pushed
the
buildKernel
branch
from
cb206e2 to
e7509e4
Compare
himanshus2025
force-pushed
the
buildKernel
branch
10 times, most recently
from
9797542 to
fbf954d
Compare
himanshus2025
force-pushed
the
buildKernel
branch
from
cee0d4c to
095e63a
Compare
himanshus2025
force-pushed
the
buildKernel
branch
from
77ea0f9 to
9a93f5e
Compare
shmuelhazan
requested review from
astrunin
and removed request for
paul-sirin
|
Looks good to me. |
himanshus2025
force-pushed
the
buildKernel
branch
2 times, most recently
from
ade70ff to
ec8d42c
Compare
shmuelhazan
changed the title
.github/workflows/build-kernel.yml
Outdated
| path: | | ||
| arch/arm64/boot/Image | ||
| .config | ||
| vmlinux | ||
| Module.symvers | ||
| modules.order | ||
| arch/arm64/boot/dts | ||
| drivers | ||
| include |
There was a problem hiding this comment.
maybe cahce all of the current dir?
There was a problem hiding this comment.
also -- won't that replace also the source files?
There was a problem hiding this comment.
Correct, adding whole drivers/includes folder replace source files.
Same would happen if we, cache all of the current directory( won't be a great strategy), also it may exceed cache limit, kernel source code with build file is more than 10 GB I think.
I came up with a better solution , only caching the generated files.
himanshus2025
force-pushed
the
buildKernel
branch
3 times, most recently
from
b3d7ce3 to
e3128d9
Compare
…ebuild cache, incase .config is changed
himanshus2025
force-pushed
the
buildKernel
branch
4 times, most recently
from
5554c59 to
5ee221f
Compare
himanshus2025
added
ready for review
There was a problem hiding this comment.
@astrunin @himanshus2025 The reason is that currently we build the DTS as a part of the kernel. We can move it to be a part of the kernel (including the defconfig), or remove it and then build the DTBs as a part of the yocto build instead.
For now, let's keep these as empty, and @himanshus2025, can you please create a task to move the DTB/DTBO builds to be inside of yocto?
Thanks
There was a problem hiding this comment.
hi @shmuelhazan We decided to remove them from Makefile. dtb file checks are already being taken care in Yocto.
meta-siklu-arm64/conf/machine/siklu-arm64.conf
There was a problem hiding this comment.
@himanshus2025 my bad. @astrunin corrected me that this is not needed. We can remove them from the Makefiles and from here.
…ue remove ipq6018-siklu-ctu-100.dtb from Makefile) (#63) Fix build issue i.e. removed ipq6018-siklu-ctu-100.dtb from Makefile. Build got passed last time due to cache : here is original pull request #61 Failure: https://github.com/siklu/linux/actions/runs/19708155136/job/56461156967
4 participants
Adding github action for building Linux kernel everytime , we make changes to kernel repo